It borrows and expands on the characterizations of Jake and Nog during A Man Alone, The Nagus and Storyteller, still making mischief and growing up, not quite to the point of jake becoming a writer or Nog wanting to join the Academy. Thus, it's an interesting, accurate look from a young adult's perspective at first season DS9 (both Jake and Nog are the youngest on the station, the only recurring kids and in Ms. O'Brien's class), but the suspense and adnveture aren't quite even up to Hardy Boys level. I'd recommend Starfleet Academy (TNG Young Adults) over this.

This book, while perhaps not of general interest, was fascinating to me, since my husband was born in Sofia, Bulgaria and was a distant relative of the author. The blindness of the participants to the events swirling around them in Europe was startling. Their concerns with business and success overrode any concern with the outside world. Marriage between cousins, uncles and nieces, was common emphasizing the clannishness of the Jewish population. This world ended with the commencement of WW II. The book definitely has a limited audience.

The book is very wordy and simply explains (in legalese) line by line the government forms you need to fill out. Also the forms on the floppy are in Macintosh Format(s) (Adobe Acrobat & some other format .rev?) If you write software and are looking for a book to verbosely explain the steps you need to take to protect your software this is it...

180 pages of more techniques than you could possibly use. The formulas are well explained, the strategies (series of 7, magic number of three, moving averages, exponential moving averages, stochastics, csi, rsi, regression analysis, etc) are also well explained. As somone who has searched for the ultimate formula, oscillator, technique or what ever for trading commodities, after reading this book, I've concluded that you can find a chart or group of charts to justify ANY idea. Given any market, depending on which combination of indicators one chooses, one could justify any decision. Now what good is that?

Haining claims to have discovered documentation that proves the existence of The Demon Barber of Fleet Street during the late 1700s - early 1800s. Unfortunately, nowhere in the book does he cite his references or make clear exactly where he found this documentation. Without this vital information, it's difficult to accept Haining's claim that Sweeney Todd actually existed. The book is a work of fiction and should be marketed as such.

While I'm grateful anyone wrote a book on the topic, this is a joyless flogging of the facts. Hard to believe such a slim book on such a rich topic is this dry and uninteresting. Haining is tight-lipped and emotionless. Just try to figure out what his tone is. It's not a good late-night tale of murder, it's not a crime dossier, it's not thrilling or even disturbing. There is no dramatic arc to his recounting of the facts. You get the sense that he would have preferred the whole story composed as numbers on a chart. It was a huge effort to pick this book up after a pause, and continue.

The author tries desperately to convince the reader that the mythical tale that inspired the Stephen Sondhiem musical in based in reality. He relies on fictional accounts of the Demon Barber to support his hypothesis. Still, it makes for quick reading, if only to hear the various accounts of the story of Sweeney Todd.

I had to use this book for my high school's senior Java programming class, an independent study style class where we had to teach ourselves Java through reading the book. Out of seven people in the class, I was the only one who was just barely able to figure out how to actually create and execute the programs that the book had us do - and I consider myself a rather good programmer. I was barely able to get myself through the book's terrible examples and descriptions through the use of another Java programming book that I had, online resources, and an uncle who works for Sun. Everyone else had no clue what to do, so I ended up teaching them how to program in Java.

The examples that this book uses first consist of copying a program out of the book and compiling it and watching it run, and later they change to copying a program off of the included disk and compiling it and watching it run.

Furthermore, concepts that you need to complete some of the problems aren't covered until a chapter or two later; we had to create a program that would get characters out of a string in Chapter 9, and the book doesn't cover the charAt() function that the program needed until Chapter 11! It was just by luck that I flipped ahead in the book and discovered it there.

I don't think that I would have minded the deficiencies this book contains if we didn't have to pay so much for it.

I told our teacher about this and he put me in charge of finding something else to use for next year's class when I'm gone. Do what I'm doing: find a different book to use.

The most remarkable job of "hand waving" I've ever read. Practically every code example uses features that haven't been discussed yet.

"Pay no attention to that wizard behind the curtain!"

Fundamental constructs like if, while, and for are in chapters 7 and 8, but advanced features like I/O and exceptions are in chapter 6. Primitive and user-defined data types are in chapter 4, but arrays are in chapter 11. Chapter 6 is titled "I/O and Exception Handling" but byte streams and character streams are in chapter 9. Relational and boolean operators are two chapters after all the other operators. Spent 2 pages in chapter 2 talking about the tag, then didn't even mention getParameter() in chapter 12 when writing applets is covered.

Inheritance is glossed over in 4 pages. AWT visual components have 6 pages waved at them. The author is able to explain FlowLayout, GridLayout, and BorderLayout in less than a page each. Even more amazing, is his ability to explain GridBagLayout in the same amount of space. Discussed Events before Components, and the very first example of an event listener is an anonymous class (with no attempt at an explanation).

Likes using variable names that start with a capital letter. Likes intermixing two different styles of curly brace instanceof, event adapter classes, inner classes, anonymous classes, overriding, overloading, Java's character data type, character literals, "functions" in Java (as a flow-of-control construct), repaint(), protected, abstract, command line arguments, parameter passing modes, the default/implicit toString(), polymorphism.

In spite of the author's very limited success at covering legitimate introductory topics, he tackles many buffering, measuring fonts, threads, exceptions, GridBagLayout, deprecated event handling.

Quotable quotes -

"Everything in Java is an object" [p39]

"Be careful when using the >= and <= operators. The order of the symbols is critical. Switching the symbols will result in an error." [p105]

"In almost all cases, your last element [in an array] will have a subscript one less than the real total." [p184]

"Interfaces are class-like groups of methods that work with your own program much like an 'assistant program'". [p211]

"You should recognize that no book can approach covering the talents and abilities of this programming language." [p253

collector's should get a copy of the Barry McGee book published in Italy by Prada back in 2002. With 300 pages of full color art plus a 20 page interview it's easily the one essential volume of Barry McGee's art. Don't even bother with this shabby collection of pamphlets or "The Buddy System" which only has about 20 pages in color. Get the Prada book-it even has an original Twist sticker on it!

I was dissapointed upon receiving this book. Actually it is not even a book, it is a collection of pamphlets from an exhibit in Philidelphia under the same name. As a fan of Barry Mcgee's artwork I was discouraged to find only a few examples of his work and mostly not even in color. I would recommend the book 'Scrawl - Dirty Graphics & Strange Characters' for someone interested in McGee and other similiar urban artists.

John Vornholt is a very two-faced star trek author, with the ability to produce ambitious and well written stories, while producing just as many naivé and brainless action adventures.

"Crossfire" is the purest example of the latter.

The main character is the drily portrayed younger version of Geordie LaForge, who works as a roadie for the Starfleet Academy Big Band, where the equally dimensionless younger version of Will Riker plays the trombone.

The book starts with the band traveling to a music competition on Pasifica, the much mentioned vacation planet of Starfleet officers.

The first half of this ridiculously short, but still overstrched story centeres around the question of the band winning or not, with tons of unnecessary and clumsy scenes filling the pages. The action begins as a bunch of Orios kidnapp the band.

Why?

Because they like the way they play, of course; no more, no less.

The band is taken to a planet where Orion troops are fighting as mercinaries in a war they've got nothing to do with, and the band is instructed to cheer them up. And of course the fighting begins just as they get there, leaving LaForge and Riker stranded together in the middle of a war zone.

Needless to say, the book has a discusting 'Happily Ever After'-ending, wich involves a lot of technobabble and a solution any reader can figure out aieons before the characters.

By the end of the book, I was truly perplexed by the question of how such a potential author could waste his time on something so utterly horrible.

This books cover the old retired exams. Wait until 2nd edition.

The Book has very little in tricks and the history is not researched verry well. Compleatly out Dated. I feal ripted off.